-
Notifications
You must be signed in to change notification settings - Fork 624
Turn BUILD_TESTING off if EXECUTORCH_BUILD_TESTS is off #12566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
[ghstack-poisoned]
Stack from ghstack (oldest at bottom): |
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12566
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New FailureAs of commit 4c2e046 with merge base 4d7f9ca ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
As the comment notes, it looks like otherwise we have third-party deps that might include(CTest) and thereby turn on testing even though our specific option is off. (Should we get rid of the specific option or more directly alias it to BUILD_TESTING?) ghstack-source-id: 50971cb ghstack-comment-id: 3081826265 Pull-Request: #12566
CMakeLists.txt
Outdated
else() | ||
# It looks like some of our third-party deps will try to turn this | ||
# on if it's not explicitly set, leading to confusing behavior. | ||
set(BUILD_TESTING OFF) | ||
endif() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you check how this behaves if you enable tokenizers? It uses abseil, which always includes CTest, which will turn on BUILD_TESTING
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that's the third-party dep I was referring to, and that CTest won't turn on testing if it's already explicitly turned off.
As the comment notes, it looks like otherwise we have third-party deps that might include(CTest) and thereby turn on testing even though our specific option is off. (Should we get rid of the specific option or more directly alias it to BUILD_TESTING?)